SJVAQS91: OPERATIONS Messages: 36 Entries..

Instrument angles: 
 
	Below are the angles for the instruments. 
site information:  latitude  =  36 degrees 48'45" 
		   longitude = 120 degrees 40'30" 
 
 
  TOWER		SENSOR		DEGREES (true north) 
 
flux tower:	uw.5m.flux	357.1 
		ati.10m.flux	357.1 
 
prop tower:	1.5m		0.0 
		3m		0.0 
		5m		0.0 
		7.5m		0.6 
		10m		0.1 
 
eddy tower:	uw.5m.eddy	359.0 
 
 

/home filled up around 2030, jd 192 
 
a little bit of archive data was lost, 
managed to fix it within about 10 minutes 
 
 

Set up covar_cosmos and covar_marigold to use prep.config 
in SJVAWS91/results/covar so that despiking can be used by 
the covars. IF CHANGES ARE MADE TO PREP.CONFIG, BE SURE 
TO CHANGE THIS VERSION AS WELL! 
 

archiving cycled for marigold 
 
This was done to enable archiving of conditional sampler data.  Unfortunately, I am already 
running a conditional sampler test.  Archiving started 22:01:42, with the cond. samp. started 
at 21:55.  I may decide to throw the air out. 
 

playing around with foil 
 
I`ve just wrapped the uw electronics boxes and the IR sensor box with foil to help 
cool them down.  It seems to be working so far, but we'll keep on watching. 
 
 

Morning status 
 
Looking at cockpits running since last night (00Z). 
 
Three spikes on (u,c).10m.ati 
 
Two spikes visible on c.5m.uw.fx 
 
w on both sonics reached +-2.5 m/s 
 
Propvane v are all negative, thus no southerly winds 
 
(G1,G3).8cm range from +50 to below -100 W/m^2 
 
G2.8cm ranges from +30 to -50 W/m^2 
 
Tsoil.a range 290 to ZZ> 315 deg K 
 
Tsoil.b 295 - 305 
 
Tsoil.c 295 to 310 
 
about 30 spikes on ().5m.uw.ed 
 
 
 

Shutdown to reset time 
 
Since our system clock is off from GMT by a few minutes, I am going to reboot aster. 
I will do this in about 15 minutes, once I've finished all of the daily plots. 
 
 

Morning status JD 196 
 
Looking through the xcockpits from last night's run. 
 
flux tower: 
 
   1. 1 spike on uw sonic 
   2. both t's look okay 
   3. pitch on uw.ed shows a significant step change; 
      is this one hooked up? 
   4. roll on uw.ed shows a small change as well; ditto? 
   5. ati sonic looks good, except for large negative offset in w 
   6. uw looks like w has a small offset also 
 
psyc tower: 
 
   1. looks ok 
 
prop tower: 
 
   1. seems ok 
 
rad farm: 
 
   1. looks reasonable 
 
eddy tower: 
 
   1. fast t, krypton and uw sonic look good 
   2. can't tell what the ir instrument is doing 
 
consamp tower: 
 
   1. three spikes on cs sonic 
   2. t.cs looks like it jumped - there is a band between about 
      30-32 C and 16-20 C, with nothing between 
 
 

O3 instrument operational 
 
 
O3 zero cals and time lag estimates 
finished. O3 instrument is now opertional, 
although the unfiltered channel shows 
noise. 
 

Morning Status, JD 197 
 
Flux tower: 
 
   1. 10m sonic and fast T okay 
   2. 5m sonic and fast T okay, although 
      there is an offset betwen the two T's 
 
Prop tower: 
 
   1. Props look ok. 
 
Psyc tower: 
 
   1. baros okay 
   3. psyc's okay 
 
Rad Farm 
 
   1. Rad okay. 
 
Eddy tower: 
 
   1. O3 looks okay, about 20 ppb? 
   2. O3.nofilter still just noise 
   3. t prime looks good 
   4. q krypton looks okay 
   5. sonic ok 
   6. co2 is anybodies guess 
 
Consamp tower: 
 
   1. no spikes on the sonic! 
 

archiving restarted 
 
I had stopped archiving while the disk was full - the tape backup is completed now. 
 
 

Morning status jd 199 
 
flux tower: 
 
   1. fast t's look okay 
   2. pitch.5m.uw.fx shows a jump 
   3. 10m.ati sonic ok 
   4.  5m.uw  sonic ok 
   5. props look good 
 
psyc tower: 
   1. look okay, except 5m wet bulb may be reading 
      a bit high 
 
rad farm: 
   1. all ok 
 
eddy tower: 
   1. o3 nominal 
   2. t.5m and krypton good 
   3. many spikes on the uw sonic 
   4. ir signals look reasonable, except 
      ir h2o mean is about 4, should be about 10 
 
 

Main breaker on xfrmr blew 
 
This happened about 30-40 min. ago.  Everything was rebooted 
and processes started.  We think this is due to all the airconditioners 
and pumps out here. 
 
 

AES aircraft made ~16 passes late this morning, 
~1200-1300 PDT.  Ian McPherson noted crop changes; 
I will compare them to crop map from Hammond (?) 
Ranch. 
 
 

Covars not running for the past hour or two. 
I stopped them in an attempt to delete the 
master .covar files, but was unsuccesful in 
doing that.  Then they would not restart 
because of problems associated with trying 
to remake the calibration files for the 
uw sonic. 
 
 

INTERNAL T in MARIGOLD: 
 
	Added internal temperature sensor to marigold 
at 16:50 gmt. 
 

COVAR files: 
 
	Around 18:50 gmt, I completed reducing the 
size of the covar files by splitting for day 206 then 
deleting ADAM.covar and renaming ADAM.covar.206 to ADAM.covar 
 
	Ragwort covar kept running ok. Cosmos and marigold 
did not. After playing around, I found I had to re-make covar 
and move it to sun4 toget them going. 
 
This was accomplished around 19:25 gmt. 
 

INTERNAL T COSMOS: 
 
	Changed the internal T sensor in cosmos to 
see if the modulated temperature data is due to the 
sensor. This was done at about 15:30 gmt. 
 

We are doing the backup tomorrow via a  
crontab job.  We have left an initialized 
tape in the exabyte. 
 
 

THIS IS A TEST: 
 
	This is to check out meta-log. 
Metalog did not want to work today. 
After many attempts the problem was found 
in the file "invl.cmt". Exactly what the 
problem was is still unknown; however, 
by copying "invl.ini" over to "invl.cmt" 
metalog started to work again. 
 
The bad invl.cmt is saved in file invl.cmt.org 
if anybody cares to look at it. 
 

COSMOS ANALOG DOWN: 
 
	Analog channels on cosmos went down 
from ~17:30 to 21:30 GMT. 
 

ADAMS BACK UP: 
 
	After putting out the fire, the adams 
were restarted. Cosmos was hung up in the vxwork 
boot menu while ragwort and marigold Ironics  
didn't boot properly. 
 
Everything was backup at 00:23 GMT. 
 

COCKPIT PROBLEMS: 
 
	cockpit has been crashing giving a warning 
message of sample.chan == 0 
 

LOGBOOK PROBLEMS: 
 
	Logbook started acting up again. 
By removing the invl.cmt file and copying 
invl.ini to invl.cmt, we got it going again. 
 

COVAR on COSMOS: 
 
	Tryed to reduce the size of cosmos.covar by 
doing a covar_split to jd 213 then renaming the file 
to cosmos.covar. The running covar did not update the 
file on the next 5 mionute interval. Therefore, I 
killed the covar task and restarted it. This took 
place around 01:45 GMT. 
 

MARIGOLD data collection stopped: 
 
	marigold data collection was stopped and 
restarted to enable analog channel 110 to be 
used by Tony for his teco. This occurred at 
19:03 GMT. 
 

CONFIG CHANGES: 
 
	Changes were made to the configuration 
files to collect data from Tony's teco unit. 
These changes were made from ~19:20 to 20:00 GMT. 
 
prep.config: turned on channel 110 of marigold 
	     did name is teco.cs 
	     amplifer gain was set to 210 and 
	     scaling set for 1000 to -1000 mvolts 
 
did.config: added teco.cs -> 924 
 
archive.config: added marigold channel 110 to 
	        archive file condsamp 
 
channel_config: turned on marigold 110 to 1 hz 
 

CONFIG CHANGES: 
 
	Changes were made to the configuration files 
to collect data from Tony's TECO unit. These changes 
took place over the time window of 19:15 to 19:45 GMT. 
 
prep.config: turned on channel 110 of marigold 
	     did name is teco.cs 
	     amplifier gain set to 2 
	     scaling set for -1000 to 1000 mvolts 
 
did.config:  added teco.cs -> 924 
 
archive_config: added marigold channel 110 to archive 
	        file condsamp 
 
channel_config: turned on marigold 110 at 1 hz 
 

POWER glitch: 
 
	A power glitch took place around 20:00 GMT. 
This was caused by an overload on the circuit going to 
marigold. Tony had powered up the TECO and the air conditioner. 
Circuit breaker was reset and everything was put back on the air. 
Tony will leave off the air conditioner for a while. 
 

MARIGOLD TURNED ON: 
 
	Due to the confusion, marigold was not turned 
on until now, 20:55 GMT (data_on). 
 

COSMOS DOWN: 
 
	Cosmos was down this morning, restarted at 
15:40 GMT. 
Based on printout from tape archive, cosmos went down at 
05:45 GMT.  
 

THE DAY of TURMOIL (214): 
 
	Below is a recap of what happened in the 
afternoon of day 214. 
 
	Tony was installing the o3 conditional sampler 
when a cicuit breaker in the transformer blew. This was 
caused by an overload of the conditional sampler AC and 
the TECO unit running on the line with the eddy tower 
equipment. Power was restored and everything looked fine. 
Approximately 10 to 15 minutes later, Dick Pearson's straw 
ignited and the ASTER firefighters were called to work. 
After putting the fire out, Tony was working again with the 
conditional sampler and power went down again. This resulted 
in a fuse in the transformer to blow. Unfortunately, we did 
not have a spare fuse. At the same time, cocklebur decided 
to quit working. Tony and Steve went to Fresno to get a new 
fuse and got power restored to the system late in the evening. 
Data was lost from about 21:00 gmt to 03:30 gmt. 
 

MARIGOLD DOWN: 
 
	marigold went down at ~23:30 gmt. 
Backup and archiving at 23:40 gmt. 
Had to reset power. 
 

COVAR FILES: 
 
	Since 19:30 gmt, I have been playing with 
the covar files to reduce the size to get back more 
disk space. The present time is 20:00 gmt. 
 

MARIGOLD ON/OFF: 
 
	Turned marigold off and on to try to 
get new conditional sampler running. This occurred 
from ~18:30 to 18:40 gmt. 
 

POWER DOWN @ TOWERS: 
 
	At ~21:15 gmt, the power at the towers 
went down. The main breaker in the distribution 
box blew. Everything came up ok and we were archiving 
data at ~21:25 gmt. 
 
	The reason for the failure may have been caused 
by the conditional sampler unit Tony was running. It 
may have been due to everything, ie, AC units, kicking 
on at the same time.